Software Vault: The Diamond Collection/The Diamond Collection (Software Vault)(Digital Impact).ISO/cdr37/spotv200.zip/SPOTCHEK.DOC

Text File | 1995-03-17 | 33KB | 784 lines

┌─────┐ ┌──────┐ ┌───────┐ ┌─────┐ ┌─┐ ┌─┐ ┌──────┐ ┌──────┐ ┌─────┐ ┌──────┐
│ ┌─┐ │ │ ┌──┐ │ │ ┌┐ ┌┐ │ │ ┌─┐ │ │ │ │ │ └┐ ┌─┐ │ │ ┌──┐ │ └─┐ ┌─┘ │ ┌──┐ │
│ │ └─┘ │ │  │ │ │ ││ ││ │ │ └─┘ │ │ │ │ │  │ │ │ │ │ └──┘ │   │ │   │ └──┘ │
│ │ ┌─┐ │ │  │ │ │ │└─┘│ │ │ ┌───┘ │ │ │ │  │ │ │ │ │ ┌──┐ │   │ │   │ ┌──┐ │
│ └─┘ │ │ └──┘ │ │ │   │ │ │ │     │ └─┘ │ ┌┘ └─┘ │ │ │  │ │   │ │   │ │  │ │
└─────┘ └──────┘ └─┘   └─┘ └─┘     └─────┘ └──────┘ └─┘  └─┘   └─┘   └─┘  └─┘


         ┌─────┐ ┌─┐ ┌─┐ ┌─────┐ ┌─────┐ ┌─────┐ ┌───────┐ ┌─────┐
         │ ┌───┘ │ │ │ │ │ ┌───┘ └─┐ ┌─┘ │ ┌───┘ │ ┌┐ ┌┐ │ │ ┌───┘
         │ └───┐ │ └─┘ │ │ └───┐   │ │   │ └─┐   │ ││ ││ │ │ └───┐
         └───┐ │ └─┐ ┌─┘ └───┐ │   │ │   │ ┌─┘   │ │└─┘│ │ └───┐ │
         ┌───┘ │   │ │   ┌───┘ │   │ │   │ └───┐ │ │   │ │ ┌───┘ │
         └─────┘   └─┘   └─────┘   └─┘   └─────┘ └─┘   └─┘ └─────┘


                   SpotChek v2.o, Written by Steve Tupy
                   Copyright (C) 1995 CompuData Systems
                            All Rights Reserved





                              SpotChek v2.o

          Copyright 1995, CompuData Systems, All Rights Reserved.
       ─────────────────────────────────────────────────────────────



     ─────────────────────────────────────────────────────────────────
     WARNING WARNING  WARNING WARNING WARNING  WARNING WARNING WARNING
     ─────────────────────────────────────────────────────────────────
     This program is  NOT FREE.  We support the  shareware concept  in
     allowing you  to try this program  out , but FULLY  expect you to
     support us  in making this program everything  it can be. This is
     something that CANNOT be done if you do not register the programs
     you use! This is NOT an option! You are entitled to evaluate this
     program for  not more than 30 days at which time you are expected
     to  either  delete  it  from  your  system(s)  or  register   it.
     ─────────────────────────────────────────────────────────────────



Introduction
────────────

  SpotChek is an Uploaded Files Processor. SpotChek will do the
  following, all of which are optional and configurable by the sysop.
  This version of SpotChek is designed to run with Clark Developments
  PcBoard BBS system, version 15.0 or higher.

- Checks to see if this file is unwanted. A TrashCan file is checked for
  filenames(wildcards accepted) and if the currently uploaded file
  matches one of the filenames, appropriate action is taken depending on
  how you configured SpotChek to handle it.

- Does a CRC check of the file to see if it is a duplicate file already
  uploaded to the system. CRC calculation of the file ensures that the
  filename can't be changed because the calculation is on the file, not
  the filename.   + Reg'd mode only.

- Imports File Id type files. These are by now an accepted standard of
  describing whats in archives. SpotChek has full support for extracting
  these files and putting them into your  DIR files as descriptions.

- Extracts the archive to a temporary directory. This allows SpotChek to
  do various processing tasks, necessary for archive conversion, virus
  scanning, and file_id insertion. Fully configurable, the only side
  effect to disabling this option is not having the above options.

- Performs a Virus scan with your favorite scanner. Merely enter the
  command line in the config program and you may use any existing Virus
  system.

- Checks to see if you want to convert all archives to a default format.
  If you do, SpotChek will recreate an archive and update all the
  necessary PcBoard files. After a succesful convert, SpotChek resumes
  the remaining tests on the file using the new format.
  +Reg'd mode only

- Performs a CRC override of the archive. This is handy if you have
  disabled the above functions, but still want to test for CRC
  integrity, or to recheck a converted archive.

- Will optionally insert a Comment file (except LHA, it does not support
  commenting) into the archive header. Any text file containing your
  comment can be used. A set of predefined macros may be used in this
  text file so that you may insert system info or file info into the
  comment with up to the minute information available, giving power to
  fully customize your comments and/or archive headers.

- Checks for files from within the archive that are undesirable. This
  may include advertisements from other BBS's or any unwanted file.
  Please remember that the difference between this and the trashcan
  is that the TrashCan checks the files name, this function checks the
  filenames from within the archive, not the actual filename itself.

- SpotChek will optionally insert a file or advertisement of your
  choice. This may again be any file you wish to insert.

- 6 Archive protocols are supported....

      1. ZIP
      2. ARJ
      3. ARC
      4. ZOO
      5. LHA (or LZH)
      6. PAK

- At any time, if the file fails any of the tests, you may optionally
  move the file to a bad/alternate directory. This may be a file with a
  virus in it, or any other thing that may have gone wrong with it. The
  alternate directory may be an offline directory that protects other
  users from downloading it, at least until you get a chance to check it
  or remove a virus etc...

- Also, at any time, if the file fails, SpotChek will generate a message
  to either the user or the sysop or both indicating which file failed,
  what time and other info you may wish to insert. You may also override
  the users current conference, and force all mail generated by SpotChek
  into your Main Conference, away from echomail scanners etc...
  A full set of macros are supported along WITH the PCB @macros@

- Two modes of operation are used by SpotChek. UPLOAD is the initial
  upload of the file and will result in all the tests being run. TEST is
  a user who is online and executing the TEST command, in which case
  SpotChek will abort the dupe check and the file_id insert as it is
  assumed it has already been done, making the processor quicker at the
  task at hand.

- Full logging is supported, including filenames and all errors SpotChek
  might encounter. You may optionally have SpotChek write to its own log
  file, located anywhere you wish, or simply have SpotChek write to the
  current default logfile for that particular node.

- "TackFiles" may be inserted onto the end of the FILE ID files, meaning
  you can append the text in this file to the end of the file id, so that
  if systems who get this file after you who also insert file id files as
  descriptions will then see the text you had inserted.

- Optionally, if there is no file_id.diz file found in the archive, SpotChek
  will take the users description and add it to the archive as a valid file
  id file. During this operation, SpotChek will insert any tackfiles
  specified.



─────────────────────────══════════════════════───────────────────────────────
                          Configuring SpotChek
                         ──────────────────────




  Fire up the configuration program, SPOTCFG.EXE, and start at the top.
SpotChek has a full built in help system that would almost ensure a
clean configure, but we will go over all the fine points here anyways.




A Note about Multi-Node Systems!!
─────────────────────────────────
  Make sure you run SpotCFG from one of your PCB directories as the
config file is saved in the current directory the config program is
running from. This way each time SpotChek runs, it will be sure to
find its configuration files. Be sure that there is a copy of the
CFG file in EACH nodes working PCB directory. In a multi node system,
each node MUST point to a unique working directory. If you fail to do
this and have all nodes extracting to one file directory, you will
surely have interesting results and files that may be "mangled" in
together if file conversion is taking place. SpotChek fully supports
multi node systems and will honor all file sharing within the PCB
envoironment.  Because of this you may notice a small box appear
near the bottom of your screen from time to time with a countown
timer in it counting down from 10 to zero. This is merely SpotChek
waiting for file access on your network. SpotChek will try this
10 second routine ONLY 5 times. If SpotChek FAILS to gain
access to your DIR files, it will write its info into the PCB
system files so that the description will be pulled into the DIR
file by PCB the next time it loads up that areas DIR file, either
from PCBFILER or from PcBoard itself. This gaurantees that you will
not lose important info about the files that are coming into your
system. This file sharing mechanism is also supported in a regular
non network envioronment, but likely will not ever be tested.


Paths/FileNames
═══════════════

- Path/FileName of "TackFile"

        A full path and filename of a textfile you can maintain and
insert as an addendum to the file id file included with most archives.
If there is no file id file, this will be ignored.


- Path/FileName of your Add File


        This is a file you wish to have added to the archive. This may
be any filename, as long as it exists. If it does not exist, SpotChek
will log an error telling you it cound not find the file.


- Path to your Temporary Directory


        Path to a work directory where SpotChek will store temporary
files it creates when extracting, file_id insertion, virus scanning and
archive conversion. This directory MUST be empty as SpotChek will wipe
it and ALL subdirectories from it that may exist, so please make sure
this path is a solo path. Here you may want to make use of a RAM drive
to increase performance and reduce on drive wear and tear.


- Path/FileName of your StripFile


        This is a file that includes one filename per line, wildcards
permitted, of all the files you want stripped out of the archive. The
main difference between this and the TrashCan function is that this
takes files from within the archive, not checking the filename itself.


- Path/FileName of the TrashCan


        This is a file that includes one filename per line, wildcards
permitted, of all the files you don't want uploaded to your system. The
difference between this and the above StripFile option is that this only
checks the filename being uploaded (eg. *.GIF) and will only act on a
violation of the filename, nothing else.


- Path to your Bad Files Directory


        Path to an optional directory you may wish to have files moved
to when a file fails, for whatever reason. You may then have the file
offline, away from prospective downloaders until you can determine if
the file can be cleaned or repaired. This may include a directory with
files already in them, they are not touched or deleted in any way.


- Path/FileName of your Log File


        This is an optional path to a file that will be maintained by
SpotChek. Please note that if the "Log to PCB" prompt on the switches
menu will override this. This will only be disabled if you have both the
log to pcb prompt set to "N" and this line blank.


- Path/FileName of Comment File


        This is a text file to be used to insert as a comment into the
archive. LHA or LZH does not support this. Please remember to leave the
first line blank for the proper formatting of the comment file while
displaying the header in the text file. If this file does not exist,
SpotChek will log an error, but no other harm is done. You may optionally
insert a series of macros into the text of this file to enhance your
archive comments that are inserted at program runtime. These are as
follows...

  %T%   Time this file was uploaded to the system. This will be in the
        format of HH:MM:SS.
  %F%   Full FileName and Extension.
  %D%   The Date the file was uploaded in the format of MM/DD/YY.
  %U%   The users name who uploaded this file, if available(MUST have
        Users.Sys File via the spot.ppe included).
  %B%   Board or System Name as it appears in your PCBSetup.
  %O%   PCB Sysops Full Name as it appears in your PCBSetup.
  %P%   SpotCheks Name and version number as well as a string telling
        you if the version of SpotChek that processed this file is
        registered or not. If it is, you will see a "Registered at the
        end of this line, otherwise "UNREGISTERED" shows up instead.
  %S%   File Size of the file uploaded, in bytes.

... these may be inserted freely into the text, but be careful how you
format the text. This will NOT work...

  ┌──────────────────┐
  │ File Name  : %F% │

  as it will show up like this...

  ┌──────────────────┐
  │ File Name  : FILENAME.ZIP │

  after it is expanded into the full text. You will have to play with this
  get the desired results. A sample file called COMMENT.TXT is included with
  the distribution archive to give you a sample of what something that
  works well with this feature looks like.


- Path/FileName of Intro Screen


        A file used for displaying the initial screen to the user. This
is a fully qualified path and name of a file that exists. If it does
not, SpotChek will ignore it and not show it. There is a sample Screen
called INTRO included with the distribution archive. Please note that
you may at any time disable this function (to further customize your
system) by simply leaving the field blank in your config program. Also
note that you may use any of the PCB color codes as they are translated
and shown to users at run time, and ANY PCB system macros may also be
used, but not all of the same ones the BBS has. Here is a list of
available macros available to SpotChek...


@AUTOMORE@
@BEEP@
@BOARDNAME@
@BPS@
@CITY@
@CLREOL@
@CLS@
@DATAPHONE@
@DAYBYTES@
@DLBYTES@
@DLFILES@
@EVENT@
@EXPDATE@
@EXPDAYS@
@FIRSTU@
@FIRST@
@HOMEPHONE@
@LASTDATEON@
@MORE@
@MSGLEFT@
@MSGREAD@
@NODE@
@NUMTIMESON@
@OPTEXT@
@PAUSE@
@POFF@
@PON@
@QON@
@QOFF@
@SECURITY@
@SYSDATE@
@SYSOPIN@
@SYSOPOUT@
@SYSTIME@
@TIMELEFT@
@TIMEUSED@
@TOTALTIME@
@UPBYTES@
@UPFILES@
@USER@
@WAIT@
@Xbf  .... where b = background color and f = foreground color
@X00
@XFF


  If you need further assistance with the description of each of these
macros, please consult your PcBoard Manual, but please remember, not all
of the macros supported by PcBoard are supported by SpotChek. As many as
possible were fit in, but limitations kept us from using all of them.
All of the above macros are supported by SpotChek.


- Path/FileName of Main Screen


        The Main Screen for SpotChek. This Screen should only ever be
designed for use with the first 19 lines. In other words, SpotChek
reserves the last 5 lines for the User box ( a small text box which
keeps the user updated on what is happening during the processing ). So
, if you created a screen which only used up the first 19 lines of the
screen, you would not have the over bleeding, or scrolling of the users
screen. There is a sample screen included called MAIN in the
distribution archive. You may leave this blank to disable the function,
but it is strongly suggested to show at least something as all SpotChek
puts to the screen is the "Windows" looking box at the bottom of the
screen. It will be changed soon to have configurable color selection.


- Path/FileName of the Failed Screen


        This is the screen shown to users upon a file failing any of the
tests configured. As before, you may use any of the macros within this
file, SpotChek will recognize them. There is a sample screen included
with the archive called FAILED which you are free to use. You may also
create your own.


- Path/FileName of the Bye Screen


        This is a file holding a screen shown to users (optionally) upon
leaving SpotChek. This may be disabled by simply leaving the field
blank. All of the above macros are supported. There is a sample screen
included with this archive called BYE. All screens are in ansi, but can
be converted to PCB color codes if you wish, or you may draw your own to
give your file processor its own flavor.


- To Sysop, Path / MsgFile


  This is a path and name of a file that holds the text you wish to use
as the message text of the message you wish to post to the Sysop upon a
file failing SpotCheks testing. This may include any of PCB's color
codes or macros, including any of the ones not included above. Also
supported in this text file are a few extra macros explained here...

  %T%   Time this file was uploaded to the system. This will be in the
        format of HH:MM:SS.
  %F%   Full FileName and Extension.
  %D%   The Date the file was uploaded in the format of MM/DD/YY.
  %U%   The users name who uploaded this file, if available(MUST have
        Users.Sys File via the spot.ppe included).
  %B%   Board or System Name as it appears in your PCBSetup.
  %O%   PCB Sysops Full Name as it appears in your PCBSetup.
  %P%   SpotCheks Name and version number as well as a string telling
        you if the version of SpotChek that processed this file is
        registered or not. If it is, you will see a "Registered at the
        end of this line, otherwise "UNREGISTERED" shows up instead.
  %S%   File Size of the file uploaded, in bytes.
  %E%   The Error Condition that caused this file to fail. It will be
        in the form "Archive Conversion" , "Duplicate File" ,
        "CRC Table Bad" or "Trashcan Fail".

... these may be inserted freely into the text, but be careful how you
format the text. This will NOT work...

  ┌──────────────────┐
  │ File Name  : %F% │

  as it will show up like this...

  ┌──────────────────┐
  │ File Name  : FILENAME.ZIP │

  after it is expanded into the full text. You will have to play with this
  get the desired results. Sample files called BADFILE.* are included with
  the distribution archive to give you a sample of what something that
  works well with this feature looks like.


- To Users, Path / MsgFile


  Same as above, this is a path and filename of a text file containing
the message text of the message you wish SpotChek to post to the user
upon a failed upload of theirs. As above, you may use PCB's color codes.
Please see above for explanation of extended macro commands.


- To Sysop, Path / Message Base


  This is the actual message base name of the base you want to write the
message to. If you can't remember the name and you have PCB set up in your
envoironment, pressing F2 will pull up all your conference info, so that
all you have to do is select the base you want the message to go to.


- To Users, Path / Message Base


  As above, but this field applies to the user and not the sysop.



Archivers / Utilities
═════════════════════


- Archive / Unarchiver Command Lines

  These are all set up for you, but if you should happen to not use the
default settings for the default archivers, you may use any one you wish.
Please remember to keep the .EXE off of the end of the name. It won't
harm SpotChek, but it does make things run a lot smoother. Default
command line parameters are provided and are adequate for most of the
"generic" archiver programs. Please make note that SpotChek supports use
of sub directories, so make sure the archiver is set to extract to sub
directories as well.

- Virus Scanner / Command Line

Memory can be a consideration here, so if your particular Virus Scanner
has any memory requirements beyond an average of 350K (this is only an
average, all systems have different configurations and may vary
slightly), you may wish to set it up to use extended memory. This is not
a fault of SpotCheks as it only maintains a minumum of memory, but it is
shelled under PCB and may not have as much memory to work with as might
be necessary to invoke your particular Virus Scanner.

- Force Failed Messages to Main?

  This is to force SpotChek to place any messages it generates into the
main conference by default. This forces SpotChek to find the appropriate
base to add the message to. If this is not set, SpotChek will place the
message in the users current conference. This may not be desirable as
you may have echo bases where you do not want internal system generated
messages getting scanned and sent out to other nodes. This toggle is
usually set to "Y"


Switches  (or Toggles)
════════

- Post Message to User on Failed Upload?

  This instructs SpotChek to post a message to the User, but only if the file
fails the upload tests you have specified. You have three options here.
You may have SpotChek not post a message at all, post a message in the
users current conference, or have SpotChek override and automatically
post the message to the main conference. This is preferrable in a
situation where you may have many echomail conferences and messages of
this type are not desirable in echomail conferences. The Main Board is
usually set to handle private messages. SpotChek will set the private
bit by default when generating its messages.

- Post Message to Sysop on Failed Upload?

  The same rule applies here as above, except that the target for this
message is for the Sysop. The "To" field will have your name entered as
it is entered in your PCBSETUP, so all your regular mail scans should
work properly, notifying you of the new mail waiting. The same three
options apply here as above.

- Move Files to Bad Dir on Failed Upload?

  SpotChek can move failed files to an offline directory or an alternate
directory so that you may investigate it later. This serves to also
protect your users from potentially bad or infected files. The file is
moved, not copied, so the original file is deleted.

- Insert File Id as Description?

  Sometimes a file called FILE_ID.DIZ is included with the archive that
is uploaded. This is quickly becoming a standard as the file id contains
info about the file that may be important to show to the users. SpotChek
supports full file_id insertion and will automatically insert the file
id in place of what the user entered as a description. If you answer "N"
to this and there is indeed a file id file in the archive, you may notice
a message from the PCB system saying "Contains FILE_ID.DIZ File" in place
of where a description should be in your upload DIR file.

- Check for Duplicates?

  SpotChek has an internal duplicate checking system which handles an
unlimited number of files  for duplicates,  using a CRC calculation of
the file contents. This ensures that the filename hasn't been changed to
fool you into thinking it is a different file. A small database is
maintained in your home SpotChek directory which is necessary for
SpotChek to record the file info. This file will grow as more files get
uploaded. For each file, SpotChek reserves 4 bytes of disk space, so if
you used a total 9999 files, you would have a 40K datafile , which is
easy to maintain. It is done automatically by SpotChek. Please remember
that the more filenames you are maintaining in the dupe database, the
longer SpotChek may take to find them, so keeping this number at a
compromise between speed and number of files handled for more power
helps in the overall performance of the program.

- How Many Files to Maintain in Duplicate List

  If the above switch is set to "Y", then this number tells SpotChek
exactly how many files to maintain in its list. Please note the size of
the file you will have to have in order for this to function.

- CRC Check OverRide?

  If for some reason you wish to not use the extract, scan, convert and
file id functions, you may still wish to simply use the CRC test on the
archive as an override. Assuming you are using the extract, scan etc,
functions, a successful extract already means the archive has a valid
CRC, so this function becomes redundant. In that case, you can shut this
feature off.

- Convert Files to Default Format?

  If you have configured SpotChek to extract, scan, and insert, you may
also convert all your files to a default format. For example, you wish
all the files to be ZIP's, and you recieve a *.ARJ file, SpotChek will
convert the file over and update all the PCB files and stats. The amount
of bytes uploaded are not changed, however, as the original number of
bytes transferred remain the updated amount the user recieves credit
for.

- Default Convert Format

  This is the 3 character format specifier. Available formats are...

ZIP, ARJ, LHA (or LHZ), ARC, ZOO, PAK.

  Entering any of these codes will tell SpotChek which format you wish
to use.

- OverRide and Write to PCB log File?

  This tells SpotChek to put all log entries into your log file
specified in your PCBSETUP. SpotChek will append this file with a
similar format to PcBoard's. If this is set to "N" and the logfile path
is a valid filename, SpotChek will append that file instead of the PCB
one.

- Check File Dates to See if They are Too Old?

  SpotChek will check the files in the archive for dates that are older than
the specified date in the field below. This is just the toggle that will
tell SpotChek whether or not to carry out the function.

- If Above = Y, Then What Date is the Cutoff Date for Failed Files?

  This is the date that will be the cutoff point for the files in the
archive. If any file in the archive is older than this date, the file
will be considered a failed file and SpotChek will act accordingly.

- Create File Id File with Description if No File Id exists in Archive?

  This instructs SpotChek to look into the archive and if no file id file
exists, SpotChek will pull the description the user entered(if available)
and add it to the archive as a valid file id file. This ensures that
ALL files coming into your system go out with file id files in them. This
supports the True two way file id concept becoming increasingly popular
on todays Bulletin Board Systems.


Colors
══════

- Box Color

  This is the color used for the actual box, not the text. The color selection
 box is easy to use, just point and hit enter. At any time while leafing
 through the selections, you may hit either F10 also to achieve the same thing.

- Raise Color

  The box can be made to appear 3 D when using this wisely. This will alter
only the left and top sides of the box, giving you shading and giving the
impression of a 3 Dimensional box, as is the case with such programs as
Windows.

- Filename Color

  The color for the actual filename in the box.

- Action Color

  During program execution, there will be many messages sent to the box. This
is the color of regular text used for actions during this time and does NOT
reflect the color of the text when the current function fails.

- Failed Box Color

  There is also a little flashing box during execution. This can be altered
during an error, as is the case with this selection. A bright color such as
red works good here as the user sees it easier.

- Ok Box Color

  As with above, when the current function is succesful, this color will
determine how the box will look.

─────────────────────────═══════════════════════───────────────────────────────
                           Installing SpotChek
                         ───────────────────────


Following is a brief explanation of how to install SpotChek copying all the
files manually and/or if you are installing an upgrade...

1 - Extract all the files in this archive into a directory specified in
    your path. Make sure all executables, and all *.hlp and *.idx files
    are in this directory also. You MUST run the config program from
    the directory you wish to run PCB from as this is the directory the
    config file will be saved to!

2 - Run SpotCFG and put in all paths and switches etc.

3 - Install the Spot.Ppe file included with this archive into your
    PCBTEXT file. MKPCBTXT <PCBTEXT> will work on this in your GEN
    directory. Line 433 must be altered to reflect a line that looks
    something like this....

!c:\pcb\ppe\spot.ppe

    This will tell PCB to run the SPOT.PPE. That PPE is only a small PPE
    that creates a USERS.SYS file as PcBoard does not include such an
    option. This is important to the function of SpotChek as it is
    needed for conference paths, directory paths , users name etc...
    Without this file, SpotChek will not know who is online at any given
    time and will bark up with a "Leave Comment to Sysop there is a
    problem with USER.SYS" message. This is not desctructive and is the
    default mode while a user is online, but SpotChek will refuse to
    post a message or refuse to run altogether if it cannot find the
    drop file.

4 - Edit a file in your PCB directory called PCBTEST.BAT. This batch
    file should include only the line...

SpotChek %1 %2 %3

    This is necessary for SpotChek as PcBoard passes certain parameters
    on the command line, which get translated by the %1 %2 etc.

          That is it, SpotChek should be fully functional, provided you
    set up everything properly. You can netmail CompuData Systems to
    gain access to support for SpotChek. (see below)

    Following are a couple of reasons why SpotChek may NOT be running
    after you have completed your install....

1 - SpotChek Fails every file coming into the system for no apparent
    reason...

    If any of the utilities run out of memory or if there is a problem
    with any of the utilities paths or config's , SpotChek will report
    an error and fail the file automatically as it will assume the
    archiver or utility came back with an error. This is often the case
    when you have a lot of TSR's loaded and have less than 512K free
    after loading up your system. One example of this is McAffees Scan
    program. It uses up alot of memory, 400+ K of memory at times, so
    in reporting back an error of 2, out of memory, the file did not
    fail so much as SpotChek THINKS it failed. By trimming down on
    system overhead such problems as this may be averted. SpotChek,
    since there are so many utilities out there, will report and abort
    on any non zero program return. Try to omit the scanner by leaving
    that line blank in the config and if you are no longer having the
    problem, try to reduce the amount of memory you are using during
    computer startup, as the virus scanner ran out of memory.

2 - The Status Bar at the bottom of the screen does not show up and
    the default main screens stats show no values.

    There was no USER.SYS file present and SpotChek did not know who is
    online, so it aborted refreshing the statusbar(which only holds user
    info anyways) and did not report the users stats on the user screen.
    Check your PCBTEXT file for the above PPE installation.

3 - SpotChek extracts the file AND still does a CRC test of the file.
    This is not acceptable because if the file passed the extract, it is
    obviously a good file, at least from the perspective of having a good
    CRC value and being readable, so doing a CRC test is not necessary.
    In the config program under Toggles, you may disable the override.
    Please note that CRC does not relate to the CRC encryption that is
    done during the duplicate file check, which uses a CRC32 value of
    the file itself, not just the name, for its CRC value. That way if
    even one character in that file is different it is not considered a
    duplicate.

───────────────────────────────────────────────────────────────────────────────

- SpotChek and CompuData Systems will be supporting this product quite
  extensively, so getting future support should not be a consideration
  in purchasing SpotChek, but an explanation is in order.

───────────────────────────────────────────────────────────────────────────────

                      IMPORTANT NOTICE ABOUT SPOTCHEK

  As of this version 2.o of SpotChek, CompuData has chosen to support and
  develop SpotChek by themselves rather than license it out to Dynagrafix
  Developments, although the support board, for conveniance, will REMAIN
  at Dynagrafix Developments at 1:229/412. All Orders can be made on that
  system as well, including the credit card orders. Also please note that
  the original author, Steve Tupy, who owns and runs CompuData Systems,
  is and will be the sole supporter/developer of this product.

───────────────────────────────────────────────────────────────────────────────
                                  Support
                               ─────═══─────

  Support is available from the Dynagrafix Developments System, but will
  be handled by CompuData System Staff. You can netmail 1:229/412, or
  tie into an echo called COMPUDATA, which may or may not be available
  to you. If you wish to find out more, please netmail us, we will get
  back to you quite quickly.